Serverless application operational recovery and manifest creation

ABSTRACT

Systems and methods for backing up and restoring serverless applications are provided. A serverless application is queried to identify the functions and services used. These functions and services are transformed into a manifest or graph that allows the relationships of the serverless application to be identified in an automated manner. The serverless application can be backed up and/or restored using the manifest.

FIELD OF THE INVENTION

Embodiments of the present invention relate to systems and methods forproviding data protection operations to serverless applications. Moreparticularly, embodiments of the invention relate to systems and methodsfor backing up serverless applications. Embodiments of the inventionfurther relate to systems and methods for automatically creating amanifest for a serverless application that is used in performing abackup operation and/or a restore operation.

BACKGROUND

Serverless applications or serverless architecture are terms that oftenrefer to applications that are packaged as stateless containers. Thesecontainers typically response to external events and interact withbackend services. The terms do not mean that no servers are involved inthe operation of a serverless application.

Serverless infrastructures that enable serverless applications, such asAmazon's AWS Lambda, allow an entity or user to execute code or softwarewithout provisioning or managing servers. A customer is typicallyrequired to pay only for compute time. A customer is not charged whentheir code is not executing. This advantageously allows an entity oruser to reduce operational costs and simplifies scaling.

Because serverless applications are an emerging technology, concernssuch as security or data protection may not be fully taken intoconsideration. This can create gaps and vulnerabilities for entities orusers that adopt this technology.

For example, the ability to backup a serverless application and/orrestore a serverless application is complicated because therelationships between the various components of the serverlessapplication are complex. In order to successfully backup/restore aserverless application, it is necessary to have an understanding of therelationships that exist between the components. Because serverlessapplications are often packaged as or include stateless containers, itis difficult to understand all of the conditions and relationships thatmay exist in a serverless application. In addition, tracking changessuch as function upgrades, service additions/removals can becometedious.

In serverless platforms, much of the orchestration capabilities aredelegated to third party vendors (e.g. AWS Lambda). Consequently, thereis no guarantee that the application as a whole will have consistentbackups. In fact, customers are usually concerned with the backing upthe backend service. Unfortunately, this will not be sufficient when theconditions of the application have changed or a newer version ofapplication function images have been uploaded.

Today, a customer can backup a serverless application by backing up allthe services that the application uses. This is performed manually andis tedious and error prone manual work. In fact, this processconventionally requires multiple backup application components to becreated and requires that the operation of these components becoordinated.

Even though many backend services have backup abilities, the challengein the context of serverless applications is coordinating the backup ofthe backend services with other components of a serverless application.Serverless applications are dynamic in nature: services change andapplications or containers are upgraded. These changes make coordinatingthe backup/restore difficult. This process is further complicated whenattempting to restore to an older point in time.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which at least some aspects of thisdisclosure can be obtained, a more particular description will berendered by reference to specific embodiments thereof which areillustrated in the appended drawings. Understanding that these drawingsdepict only example embodiments of the invention and are not thereforeto be considered to be limiting of its scope, embodiments of theinvention will be described and explained with additional specificityand detail through the use of the accompanying drawings, in which:

FIG. 1 illustrates an example of a serverless application and of a dataprotection system configured to perform data protection operationsincluding backup and/or restore operations for the serverlessapplication;

FIG. 2 illustrates an example of a manifest that is automaticallygenerated and that is used to perform a data protection operation; and

FIG. 3 is an example of a flow diagram of a method for performing a dataprotection operation and, more specifically, for automatically creatingor generating a manifest that is used in performing the data protectionoperation.

DETAILED DESCRIPTION OF SOME EXAMPLE EMBODIMENTS

Embodiments of the invention relate to systems and methods forperforming data protection operations for serverless applications.Protecting serverless applications or performing data protectionoperations includes at least backing up and/or restoring serverlessapplications.

Embodiments of the invention further relate to generating a manifest. Amanifest allows relationships between the various components of aserverless application to be identifies such that a backup operation ora restore operation can be performed effectively and automatically. Themanifest allows the serverless application to be defined and protected.The manifest also allows relationships between the components of aserverless application to be understood so that the serverlessapplication can be backed up and/or restored successfully.

Serverless applications often depend on third-party services or backendservices. This may be referred to as BaaS or “backend as a service”.Serverless applications also depend on custom code that may be executedor in or from ephemeral containers. This may be referred to as FaaS or“Function as a Service”. In one example, an ephemeral container relatesto software that isolates applications. Thus, the software in onecontainer is isolated from the software in another container.

Advantageously, ephemeral containers (or containers) allows multipleapplications to be isolated on the same hardware. In addition,containers allow an application to be run anywhere. This furtherfacilitates FaaS because a provider (e.g., a datacenter or a cloudprovider) can store multiple applications that are isolated from eachother and that are independent of each other.

In one example, a serverless application includes three types ofrequired artifacts or components. Together, these artifacts allow theserverless application to operate in production.

The components of a serverless application include backend services.Databases, object stores, persisted messaging services, real-timecommunication systems, file storage, social networks, searching,authentication and authorization, and payment systems are examples ofbackend services. Every service that can store long term state for anapplication are also examples of backend services. Often, the data of aserverless application may be stored or processed in or by a backendservice.

Another artifact or component of a serverless application relates toapplication functions. Application functions are a set of statelessfunctions packaged as containers that are invoked according to theapplication's function mappings. The application functions can interactwith the backend services to read, write and store state or performother tasks. A serverless application may include more than onefunction. Each function may be stored in its own container. Thus, thefunctions can be operated on (removed, upgraded, edited) independentlyof other functions of the serverless application.

Another artifact or component relates to the application's functionmappings. A serverless application requires a set of conditions thatinstruct the platform to activate the application functions. Commonexamples of these conditions include reactions to events of backendservices (e.g., an object uploaded to an S3 bucket, a transactioncommitted on a relational database, a message sent to or received by aqueue). Other common examples are reactions to events at an assigned URLendpoint (e.g., when a post request arrives atmy-app-dns/my-app-api/data). The conditions can be simple or complex.

When an event occurs, the event is effectively mapped to one or morefunctions, which are then performed. For example, detecting an imageupload may cause the image to be stored, compressed, encrypted, or thelike in the backend service. The exact function depends on the event (orrequest), the function, and the backend service.

FIG. 1 illustrates an example of a serverless application 100. Theserverless application 100 includes application functions mapping 102,application functions 104, and backend services 106. When a backupoperation or restore operation is performed, each of these components isbacked up or restored. Embodiments of the invention perform thebackup/restore operation using a manifest to ensure that all componentsare backed up or restored in a manner that allows the proper operationof the serverless application to be achieved.

In one example, the application functions mapping 102 maps events orrequests to functions. The event or request may occur or be detected inmore than one way. For example, an event at a backend service may bemapped to an application function. When a message is received as amessage service (e.g., a backend service), an event has occurred. Thisevent may then be mapped to one or more functions. The mapping candepend on various conditions (e.g., type of message, time of message,content, sending device, or the like). The event is then mapped to anapplication function 104 and the function is then performed. Forexample, the message may indicate that a client has a set of files to beuploaded to storage. This event is mapped to a function that uploads thefiles to the storage. The functions, as previously stated, may beembodied as containers that have no state.

FIG. 1 also illustrates a backup server 110 (or backup application) thatmay be configured to generate a backup of the serverless application100. The backup server 110 may perform the backup operation based on amanifest 108, which may have been generated by the backup server 110.Often, the manifest 108 is generated or exists prior to performing thebackup operation. Further, more than one manifest may exist. Point intime backups, for example, may each be associated with their ownmanifest such that the serverless application can be restored at variouspoints in time.

In addition, the manifest 108 can be generated automatically. Thegeneration of the manifest 108 typically requires that one or morequeries be made to the serverless application 100. After the manifest isgenerated, a backup operation may be performed. The resulting backup maybe stored in backup storage 112. The backup storage 112 may be anysuitable device and may be cloud-based.

When taking into consideration continuity requirements (e.g., businesscontinuity requirements), embodiments of the invention are able toperform operational recovery to curtained points in time as required,for example, by the application's service level agreement (SLA).

Embodiments of the invention thus relate to systems and methods thatautomatically create or generate the manifest 108. Embodiments of theinvention are able to understand which set of components effectivelyconstitute a single application and then protect that singleapplication. Further, embodiments of the invention are able tounderstand the backend services used by the serverless application andcreate a manifest automatically to reflect this understanding and enablethe performance of backup, restore, and/or other data protectionoperations.

In order to create the manifest 108, the backup server 110 (which may beimplemented as a serverless application itself) may obtain a list offunctions that a user or entity is using the serverless environment.This may be achieved by issuing a list-functions command to theserverless application. The triggers for each such function will also beobtained. The triggers may include how a function is configured to becalled, the code of the function and the environment variables of thefunction, which usually describe the services the application uses, suchas which databases, data stores, messaging services, etc. In addition toa list-function command, this information may be obtained by issuingcommands such as get-function-configuration or get-function commands.

The functions/backend servers may describe more than one serverlessapplication. Advantageously, embodiments of the invention have theability to backup and restore at the level of a single application.

To create a backup of an application, it may be necessary to know whichpersistent services are used by the application and to back up all thesepersistent services, when backup is called. When a restore is called, itmay be necessary to restore all of the relevant services as well.

A serverless application, as previously stated, includes multiplefunctions, multiple services (object storage, data bases), connectivitybetween the functions (i.e. function can call each other), mappings, andthe like.

If there is more than a single application deployed on the same account,then functions which belong to different applications will not call eachother, will not be triggered by the same trigger, and will not write orcommunicate with the service. This allows a single application to beidentified during the creation or generation of a manifest and allowsfor the manifest to distinguish between multiple serverlessapplications.

In one example, a manifest may be created or generated as follows.Generating the manifest may include creating a graph, which representsthe relationships present in a serverless application and which allows asingle serverless application to be identified so that thebackup/restore operations can be performed at the level of a singleapplication.

The graph contains vertices for each service (for example an S3 bucket,a dynamo DB table, etc.). A vertex may be created for each function aswell.

For each function, the trigger calling the function will be evaluated orprocessed. If the trigger is a persistent service (like an object storebucket), an edge will be created between the vertex of the function andthe vertex of the service. The vertices can be created as the list offunctions, environment variables, and triggers is parsed in response tothe queries (get functions, list functions or other suitable command).

For each function, the environment variables defined by the functionwill be evaluated. If an environment variable references a persistentservice, an edge will be created between the persistent service vertexand the function vertex.

The code of the functions will also be parsed to determine if a functioncalls or references another function. If a function calls anotherfunction an edge will be created between the functions.

A single serverless application may then be defined as the connectedvertices or components of the graph. By way of example, if two (or more)components or vertices have no connection to the rest of the graph, thisindicates that these components do not affect the persistent state ofthe other components in the rest of the graph. As a result, they can betreated as a separate application.

Because a service can be accessed directly via the code, the code may beparsed to identify services that are accessed and these relationshipswill be added to the manifest.

Services may also be identified by environment variables which areconfigured with the functions. The variables may identify a service forexample such that the services to be backed up can be identified.

Once the notion of an application is obtained, all of the backendservices and functions that the application is using are reflected inthe graph or in the manifest. A backup copy of the application can thenbe generated in part by backing up each service and function ifnecessary. Further, the backup (and the restore) may be based on thegenerated manifest.

The manifest will include the current versions of the functionsincluding the code (the code may be referenced in the manifest), and thelist of services that needs to backed up. Every time a new function iscreated or a function is modified, the backup manifest will need to bechanged or updated. A new manifest could also be generated as the oldmanifest may be used in restoring to a prior point in time.

The backup system may automatically call a detection process and createa new manifest. Embodiments of the invention allow the serverlessapplication to be automatically detected and provide and the ability tobackup the serverless application with no manual intervention. Inaddition, the manifest can be automatically changed or updated, whichallows the process of automatically backing up the serverlessapplication to continue even as the application changes or is updated.

Embodiments of the invention advantageously detect a serverlessapplication automatically and provide the ability to back up theserverless application with no manual intervention. Embodiments of theinvention further update the manifest automatically, which allowscontinuation of backups even in the context of application changes.

FIG. 2 illustrates an example of a serverless application and a manifestcreated or generated from the serverless application. FIG. 2 furtherillustrates an operation of a serverless application.

In FIG. 2, ab request 202 may detected by or received at a gateway 204.The gateway 204 may be a URL for example and the request 202 may be anhttp request (e.g., put, post, get). The serverless application may becloud based and may be accessed by a client over the Internet. Exampleclients include desktop computers, laptop computers, mobile devices,tablets, or the like.

The gateway 204 is configured to process the request 202 with respect toapplication function mappings. In one example, the request 202 may beparsed and mapped to functions by the gateway 204. Thus, the gateway 204may map the request or event to one or more functions. After identifyingthe appropriate function or functions for the request 202, the functionis invoked 206. The invoked function may be embodied as a container. Thefunction 208 then performs its corresponding function based on therequest 202 or based on information received from the gateway 204.

The function 208 (or functions) may be instantiated from a containerimage. As previously stated, the serverless application or portionsthereof may be embodied in ephemeral containers. The function 208 mayinteract 210 with one or more of the of the backend services 212 and214.

The request 202 is an example of an event. Example events includeuploading an object to a storage bucket (cloud storage), a transactionbeing committed to a database, a message sent to a queue, or the like.The request may also be an http request (e.g., a post request).

The serverless application may be backed up regularly, for example by abackup server 250 or other device. The server 250 may generate amanifest 220 that allows the various components of the serverlessapplication to be identified and backed up and restored. Further, themanifest 220 is generated automatically and the backup may be performedautomatically. In addition, as changes to one or more of the componentsof the serverless application occur, these changes may be detected andthe manifest 220 may be updated or a new manifest may be generated.

A serverless application can be backed up by backing up all the servicesand functions that the serverless application uses. Conventionally, thisis a tedious error prone manual work that requires creating a lot ofpieces of the backup software and coordinating all of the variouspieces. By creating the manifest 220 in an automated manner and in amanner that adapts to changes in the serverless application, themanifest 220 can be used to create consistent backups of the serverlessapplication in a time curtained manner.

Serverless applications are dynamic and services can be easily added orremoved. If a user or entity wants to restore an older point or anearlier version of the serverless application, it may be necessary torestore services that may have been removed. The manifest 220 may be arepresentation of a plurality of manifests, each corresponding to apoint in time.

The manifest 220 represents the components of the serverless applicationand also represents the relationships between the components of theserverless application. In one example, the manifest 220 may berepresented by a graph, such as illustrated in FIG. 2. However, themanifest 220 may also be represented in other forms.

The application functions 208 and the backend services 212 and 214 arerepresentative of any number of, respectfully, functions and services.In creating or generating the manifest 220, A vertex may be created foreach service and for each function. In this example, the servicevertices 224, 224, and 230 correspond to the backend services 212 and214. The application functions 208 may include any number of functions.The function vertices 222, 226, and 232 are added to the manifest 220.

The vertices in the manifest 220 can be created as the serverlessapplication is parsed (e.g., as the functions are parsed or as thefunction's code is parsed).

Each function is then evaluated, for example by parsing the function.The triggers or conditions for the functions are identified andevaluated. If the trigger is a persistent service, an edge between thevertex of the function and the vertex of the service may be created. Forexample, the edge 236 between the function vertex 222 and the servicevertex 224 may be created. The edge 236 may contain information or beassociated with information to represent the trigger, the condition, orthe relationship between the function and the service.

The environmental variables of the functions are also identified andevaluated. If an environmental variable references a service, an edge iscreated between the function vertex and the service vertex. In thisexample, the edge 238 may represent an environmental variable withrespect to the function vertex 222 and the service vertex 228. The edge238 may thus identify the environmental variable or contain informationidentifying the relationship between the function associated with thefunction vertex 222 and the service associated with the service vertex228.

As the functions are parsed, relationships between functions (e.g., afunction that calls another function) are identified. Theserelationships are also included in the manifest 220 as edges. The edge234, for example, may represent a relationship between two functions andis represented as an edge 234 between the function vertex 222 and thefunction vertex 226. The edge 234 may also include informationidentifying why the function is called, parameters of the call, or thelike.

The edges 240, 242, 244 and 246 similarly correspond to or identifyrelationships between the components of the serverless application.

Once the manifest 220 is generated, applications can be defined based onconnected components. Assume, for example, that the edge 244 was notpresent in the manifest 244. In this case, the graph would effectivelyrepresent two serverless applications that can be backed upindependently at least because they do not affect the state of eachother: one with the vertices 222, 224, 2226 and 228 and one with thevertices 230 and 232.

Because the vertices 230 and 232 have no connections or edges to theother vertices, the functions and services associated with the vertices230 and 232 have no effect on the persistent state of the functions andservices associated with the vertices 222, 224, 226 and 228. As aresult, the vertices 248 can be treated and backed up as a singleserverless application. Similarly, the portion of the graph associatedwith the vertices 222, 224, 226 and 228 can be backed up as a singleserverless application. When the edge 244 is present in the manifest220, the manifest identifies or corresponds to a single applicationrather than two separate applications.

FIG. 3 illustrates an example of a method 300 for generating or creatinga manifest. Initially, a graph (or other representation) is generated302. This may include establishing vertices for each function andservice. The functions and services are identified, for example, byquerying the serverless application and or when the code of thefunctions is parsed. Thus, a vertex can be added at any time during thegeneration of the manifest.

During or after the code is parsed, triggers are identified and added304 to the manifest. A trigger may be associated with a request or acondition. For example, a request to upload a photo or other data to acloud storage device may be treated as a trigger that results in afunction being invoked. Thus, the trigger is related to both thefunction and the service. An edge is thus added to the manifest toreflect the trigger. Edges are added for all detected triggers.

Next, environmental variables are identified and added 306 to themanifest. In one example, an environmental variable is added when theenvironmental variable references a service. This thus reflects that theenvironmental variable is related to both the function and the serviceand should be reflected in the backup.

For example, an example of a variable can be SQLDBaddress=10.76.55.44:/DB/. This states that the SQL databased referencedin the application is in the specified IP address. This identifies whichdatabase to backup.

The functions are then parsed 308 to identify function calls. If afunction calls another function, this relationship is included in thegraph.

After the functions are parsed and the graph is created, the serverlessapplication can be defined 310. The resulting graph may result in morethan one application. If a group of vertices has no connections or edgesto another group of vertices, these two groups can be treated asseparate applications. Of course, they can also be backed up as a singleapplication. In one example, the lack of edges indicates that the stateof one group is not dependent on the state of the other group. Thus,they can be treated separately.

After the graph is created, a backup application can be performed usingthe graph. The graph allows all of the related functions and services tobe backed up such that the resulting backup is consistent. Services orfunctions that affect the state of other functions or services areprotected in a consistent manner.

Example Computing Devices and Associated Media

It should be appreciated that the present invention can be implementedin numerous ways, including as a process, an apparatus, a system, adevice, a method, or a computer readable medium such as a computerreadable storage medium or a computer network wherein computer programinstructions are sent over optical or electronic communication links.Applications may take the form of software executing on a generalpurpose computer or be hardwired or hard coded in hardware. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention.

The embodiments disclosed herein may include the use of a specialpurpose or general-purpose computer including various computer hardwareor software modules, as discussed in greater detail below. A computermay include a processor and computer storage media carrying instructionsthat, when executed by the processor and/or caused to be executed by theprocessor, perform any one or more of the methods disclosed herein.

As indicated above, embodiments within the scope of the presentinvention also include computer storage media, which are physical mediafor carrying or having computer-executable instructions or datastructures stored thereon. Such computer storage media can be anyavailable physical media that can be accessed by a general purpose orspecial purpose computer.

By way of example, and not limitation, such computer storage media cancomprise hardware such as solid state disk (SSD), RAM, ROM, EEPROM,CD-ROM, flash memory, phase-change memory (“PCM”), or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother hardware storage devices which can be used to store program codein the form of computer-executable instructions or data structures,which can be accessed and executed by a general-purpose orspecial-purpose computer system to implement the disclosed functionalityof the invention. Combinations of the above should also be includedwithin the scope of computer storage media. Such media are also examplesof non-transitory storage media, and non-transitory storage media alsoembraces cloud-based storage systems and structures, although the scopeof the invention is not limited to these examples of non-transitorystorage media.

Computer-executable instructions comprise, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing device to perform a certain function orgroup of functions. Although the subject matter has been described inlanguage specific to structural features and/or methodological acts, itis to be understood that the subject matter defined in the appendedclaims is not necessarily limited to the specific features or actsdescribed above. Rather, the specific features and acts disclosed hereinare disclosed as example forms of implementing the claims.

As used herein, the term ‘module’ or ‘component’ can refer to softwareobjects or routines that execute on the computing system. The differentcomponents, modules, engines, and services described herein may beimplemented as objects or processes that execute on the computingsystem, for example, as separate threads. While the system and methodsdescribed herein can be implemented in software, implementations inhardware or a combination of software and hardware are also possible andcontemplated. In the present disclosure, a ‘computing entity’ may be anycomputing system as previously defined herein, or any module orcombination of modules running on a computing system.

In at least some instances, a hardware processor is provided that isoperable to carry out executable instructions for performing a method orprocess, such as the methods and processes disclosed herein. Thehardware processor may or may not comprise an element of other hardware,such as the computing devices and systems disclosed herein.

In terms of computing environments, embodiments of the invention can beperformed in client-server environments, whether network or localenvironments, or in any other suitable environment. Suitable operatingenvironments for at least some embodiments of the invention includecloud computing environments where one or more of a client, server, ortarget virtual machine may reside and operate in a cloud environment.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. A method for backing up a serverless application,the serverless application including backend services, applicationfunctions, and function mappings, the method comprising: adding functionvertices and service vertices to a manifest, wherein each functionvertex corresponds to a function of the serverless application and eachservice vertex corresponds to a backend service; identifyingcharacteristics of each function; adding the identified characteristicsto the manifest as edges between the function vertices and the servicevertices; evaluating the manifest to identify components of theserverless application that impact a persistent state, wherein thefunction vertices and the service vertices that are not connected toother function vertices or service vertices by an edge are not includedin the serverless application and do not impact the persistent state;and backing up the identified components as a single serverlessapplication, wherein the function vertices and the service vertices thatdo not impact the persistent state of the identified components arebacked up as a different serverless application.
 2. The method of claim1, wherein the characteristics include triggers, environmental variablesand/or function calls.
 3. The method of claim 2, wherein the manifestcomprises a graph, further comprising adding the triggers, theenvironmental variables and/or the function calls as edges in the graph.4. The method of claim 1, wherein the identifying characteristics ofeach function includes parsing each function to identity triggers,environmental variables, and/or function calls.
 5. The method of claim1, wherein the evaluating the manifest to identify the components of theserverless application that impacts a persistent state includesidentifying a group of vertices connected by edges as the serverlessapplication, wherein vertices that do not have a path to other verticesin the group of vertices are not included in the serverless applicationand are identified as the different serverless application.
 6. Themethod of claim 1, further comprising querying the serverlessapplication with one or more queries to obtain a list of functionsand/or services.
 7. The method of claim 6, wherein the one or morequeries include a list functions command, a get function configurationcommand and/or a get function command.
 8. The method of claim 1, furthercomprising detecting a change in the serverless application andgenerating a new manifest in response to the detected change.
 9. Themethod of claim 8, further comprising backing up the serverlessapplication based on the new manifest.
 10. A non-transitory storagemedium having stored therein instructions that are executable by one ormore hardware processors to perform operations comprising: addingfunction vertices and service vertices to a manifest, wherein eachfunction vertex corresponds to a function of the serverless applicationand each service vertex corresponds to a backend service; identifyingcharacteristics of each function; adding the identified characteristicsto the manifest as edges between the function vertices and the servicevertices; evaluating the manifest to identify components of theserverless application that impact a persistent state, wherein thefunction vertices and the service vertices that are not connected toother function vertices or service vertices by an edge are not includedin the serverless application and do not impact the persistent state;and backing up the identified components as a single serverlessapplication, wherein the function vertices and the service vertices thatdo not impact the persistent state of the identified components arebacked up as a different serverless application.
 11. The non-transitorystorage medium of claim 10, wherein the characteristics includetriggers, environmental variables and/or function calls.
 12. Thenon-transitory storage medium of claim 11, wherein the manifestcomprises a graph, further comprising adding the triggers, theenvironmental variables and/or the function calls as edges in the graph.13. The non-transitory storage medium of claim 10, wherein theidentifying characteristics of each function includes parsing eachfunction to identity triggers, environmental variables, and/or functioncalls.
 14. The non-transitory storage medium of claim 10, wherein theevaluating the manifest to identify the components of the serverlessapplication that impacts a persistent state includes identifying a groupof vertices connected by edges as the serverless application, whereinvertices that do not have a path to other vertices in the group ofvertices are not included in the serverless application and areidentified as the different serverless application.
 15. Thenon-transitory storage medium of claim 10, the operations furthercomprising querying the serverless application with one or more queriesto obtain a list of functions and/or services.
 16. The non-transitorystorage medium of claim 15, wherein the one or more queries include alist functions command, a get function configuration command and/or aget function command.
 17. The non-transitory storage medium of claim 10,the operations further comprising detecting a change in the serverlessapplication and generating a new manifest in response to the detectedchange.
 18. The non-transitory storage medium of claim 17, furthercomprising backing up the serverless application based on the newmanifest.